From: Anton Gladky <gladk@debian.org>
Date: Thu, 12 May 2022 21:48:46 +0000 (-0500)
Subject: Manually specify git commit hash
X-Git-Tag: archive/raspbian/3.2+dfsg-2+rpi1^2~6
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/success//%22http:/www.example.com/cgi/success/?a=commitdiff_plain;h=f5296a2d0ce6dc53f65c26ebed08ab6177c9c17c;p=solvespace.git

Manually specify git commit hash

Revise on every upstream update!

Forwarded: not-needed
Last-Update: 2022-06-30
===================================================================

Gbp-Pq: Name 01_hardcode_git_hash.patch
---

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 11adeb5..bddb6e2 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -36,9 +36,9 @@ endif()
 # NOTE TO PACKAGERS: The embedded git commit hash is critical for rapid bug triage when the builds
 # can come from a variety of sources. If you are mirroring the sources or otherwise build when
 # the .git directory is not present, please comment the following line:
-include(GetGitCommitHash)
+# include(GetGitCommitHash)
 # and instead uncomment the following, adding the complete git hash of the checkout you are using:
-# set(GIT_COMMIT_HASH 0000000000000000000000000000000000000000)
+set(GIT_COMMIT_HASH 70bde63cb32a7f049fa56cbdf924e2695fcb2916)
 
 string(SUBSTRING "${GIT_COMMIT_HASH}" 0 8 solvespace_GIT_HASH)
 project(solvespace